Every coder is going to understand that “water time” is different from “time” or “datetime”?
Every coder is going to know how to convert “water time” to/from “time” or “datetime”, and be able to do the math?
No user will ever want more than 63 units?
If so, you have a winning solution.
It appears I am way out of my element. In the few open source projects that I have contributed, no one has ever exposed their own data types. This sounds like to much dependence on other people. I am still of the belief, if the function for storing the time accepted a standard time data type, none of this would be an issue.