Either way, it may indeed be beneficial to return time as a double - so code which stores it in floats will not care about the change, but the code which uses it in intermediate calculations will and it will potentially benefit from it. Notes taken!
EDIT:
Will generate more code warnings of course, but I believe it's a good tradeoff, since the game has a ton of them anyway and going through them all is something for another day.
Things like using a bit weird data types (floats instead of doubles) and writing functions thousands (!) of lines long.
Then asking me why did the reconstruction have a weird circular error around the origo...