When a TIME column specifies a precision greater than 3, there will be data loss for any micro or nanoseconds because SqlServerChangeTablePointer#getColumnData relies on using ResultSet#getTime which only supports millisecond precision.

Could we return a Timestamp or a LocalTime value instead that will carry a much more precise precision value so that the micro or nano second precision isn't lost?