> Ironically, the fact that the bad time calculation had been improved in some parts of the code, but not all, contributed to the problem, since it meant that t

> Ironically, the fact that the bad time calculation had been improved in some parts of the code, but not all, contributed to the problem, since it meant that the inaccuracies did not cancel. ----------- I wonder what trade-off informed their decision not to have the time code in one place and pass it around as they needed it. Or at least defined in one place and then inserted where they needed it if there was some requirement that it be right there in the functions that wanted to know about time. :/ Just seems a danged odd thing to do.