Saxon

The first problem is caused by the code internally using the constructor that expects microseconds rather than nanoseconds.

The second problem is a side-effect of the fact that due to arithmetic overflow, the number of nanoseconds held in the value is negative.

I have changed a number of places that used the old microsecond contstructor to use the new nanosecond constructor in its place. In most cases the only adverse consequence was a loss of precision, e.g. when converting xs:dateTime to xs:time.