Go's time package claims giving a nanosecond precision.
<http://golang.org/src/pkg/time/time.go>

I'm wondering how it is implemented and if I can trust it. My doubts come from Python, which clearly documents its difficulties and limitations with time:

> 
> *From <http://docs.python.org/2/library/time.html>*
> 
> 
> The precision of the various real-time functions may be less than
>  suggested by the units in which their value or argument is expressed.
>  E.g. on most Unix systems, the clock “ticks” only 50 or 100 times a
>  second.
> 
> 
> On the other hand, the precision of time() and sleep() is better than
>  their Unix equivalents: times are expressed as floating point numbers,
>  time() returns the most accurate time available (using Unix
>  gettimeofday() where available), and sleep() will accept a time with a
>  nonzero fraction (Unix select() is used to implement this, where
>  available).
> 
> 
> 

Since the operating systems are giving such a hard time to python, how does Go achieve its nanosecond precision?