> What's the granularity? I want better than seconds. It's not that I think
> the clocks are accurate, but more bits tends to avoid sort collisions even
> when they are bad bits.
Hang on, I'll look it up.
Okay, the datum in a CFDate is actually a double precision floating point value in seconds since (or before) the epoch. The dynamic range, therefore, is +- DBL_MAX (1.7976931348623157e+308) seconds, and the smallest interval it can resolve is DBL_EPSILON (2.2204460492503131e-16) seconds. What granularity you can actually get from the host for a timestamp is system-dependent.
I think that this will do the trick.
-jcr