Fix for reported off-by-one (nanosecond) error in RelTime

User reported this error with a test case.  I'm not entirely sure how
it's different from existing cases, but it does appear to do something
undesirable.
2 files changed