Well, you could use:
I'm not convinced it's worthwhile though, because there's some overhead in launching a child process for communication this way, and I think it would wipe out the extra resolution you're after.
You could potentially run a background "slave" process which sat listening for requests for the time, which responded with the date. That way you could do the ipcBeginProcess() once, and then send a "command" to the child to request the date whenever you wanted the current date, and it would feed it back.
One way to do this would be to use a little C program like this:
struct timeval time;
I compiled this with "cc -o datequery datequery.c" and then use this SKILL:
unless(CCSgetDate.cid && ipcIsAliveProcess(CCSgetDate.cid)
and then call CCSgetDate() whenever you want the date (in form seconds.microseconds).
Alternatively, if you're trying to optimize code, you could use the SKILL profiler, or use the cputime() function in SKILL. Depends really what you're trying to achieve.