> I thought monotonicity meant that (DateAndTime now) >= (DateAndTime now)
> would always be true. In other words, "DateAndTime now" considered as
> a function wo elimiated the would always be non-decreasing.

That is what it means.

>
> As Avi points out elsewhere, if you evaluate "DateAndTime now" faster
> than the resolution of the clock, you should get the same value.

Aye, that is why my original implementation kept track of the last 
instance of DateAndTime instanciated by DateAndTime class>>#now and 
advanced it by one nano-second if the evaluation occured faster than the 
milli-second clock resolution.

Regrettably the rest of the #now method was very broken. Avi fixed it but 
took out the montonic functionality.

I will get round to merging the original code with Avi's code.

Cheers

Brent