Latency computation shows negative value occasionally

On a couple of results the computed latency reads as a negative number of milliseconds. Clearly a clock/ordering bug between two of the timing points. Makes it useless for judging the best fire moment.