Clock fuzzing bugs

[Hal Murray]

esr at thyrsus.com said:
> If we don't see any evidence of beat-induced quantization, I'm willing to say
> we drop this code. 

How about adding a --disable-fuzz configure option so we can experiment 
without breaking the default case.

Or maybe a runtime configure option.

--------

Early Raspberry Pis have a 1 microsecond tick,  It takes a bit less than that 
to read the clock.  If you are lucky, you can read the clock twice and get the 
same answer.



-- 
These are my opinions.  I hate spam.