Of clocks and simulation, betimes and otherwise

The other thing I needed to mention about the time message that has to change: two fields for the timestamp. Two fields – really? Is there some advantage to it? A single 64bit nanosecond value would be infinitely more handy in my mind. I can read and write that atomically with no extra work on my common x64 platforms. I’ve had to resort to std:atomic for the current time message just so I don’t accidentally read a nanosec value with the wrong sec value. It’s not pretty.