Tour order not consistent with arrival/departure times

[bhargavasana]

We noticed that tour order is not consistent in DaySim outputs. For example, here are the tour records for a person:

I do not recall DaySim violating temporal consistency in the past. Now, we are finding that a lot of tours (more than 20%) have this issue. Have there been any changes to the relevant code?

[jhelsel11]

There could also be a problem in the trip file with overlapping trips. For example here are the records for hhno = 46712, pno = 2:

Trip 7 runs from 1192 - 1264, but trip 8 runs from 1214-1218 and trip 9 runs from 1232 - 1236. As you can see from the corresponding tour file records below, there is no parent/subtour relationship.