Times ending in x:xx.100 or x:xx.10 are hard to differentiate. However, there is a bug in the game for the final screen if you end on the frame after x:xx.97.5. It will literally display "100" in your milliseconds place, not 10 milliseconds. For these runs, I will need to add those milliseconds into the seconds place. It is easy to catch these because it's the only number it occurs for and the timer passed x:xx.10 through x:xx.9x until it stops on the x:xx.10 again.
This was discussed between myself and Ihavenonamesda back in 2014, but didn't get caught on runs until more and more runs came in. I've done my best to keep my eye out for one, and this is one I got today: http://www.speedrun.com/run/y8q1ev1y
To compare, this is a run with a real x:xx.10 ending: http://www.speedrun.com/run/mk42koly
A real 1:53.10 run would display as a 1:53.10. A 1:54.00 would display as a 1:53.100 (1 minute, 53 seconds, and 100 milliseconds (aka 1 second)).
The only time the third decimal is appropriately used is when it is a "5", such as .175 or .975, which is displayed as "1:53.97.5", splitting the milliseconds even farther.
