Actually, I can't decide if this is an example of bad coding, or of the limitations of doing fast target tracking using a system that has huge time granularity in its clock. Granted, the technology is old... so it's probably got less power than my wristwatch... but 0.1s is not a good tick width if you're trying to intercept something that can move 168 meters during that time.

It is unclear from this writeup whether this is a limitation born of hardware, or in software. Regardless, the 24bit truncation on casting to real was a pretty egregious software error. If your time resolution is both mission critical and crippled in hardware, then don't perform software operations that further limit it.