Fix matching XMLs to Chronobox SEQ_RUNNING hits for very close sequences

[DJDuque]

The XMLs have a 1s granularity. Currently, they are matched to Chronobox hits by the closest match within a given tolerance. If sequences start running within 1 second, they both match to the same SEQ_RUNNING chronobox hit. This is not a very big issue, because this mostly happens for e.g. rct_botg sequences that don't have an event table. But it might bite us in the future if there is a very quick sequence with an event table run in a loop.

This can be tested with e.g. run 10620