I can choose "Date and time (2)" as the data type for a column in TimeXtender. This sets the actual SQL datatype as datetime2(7).
But Datetime2 supports precision between 0-7, e.g. datetime2(0) for no millisecond precision. The storage requirement varies with precision, so there's a storage benefit to choosing lower precision.
It would be nice if we could choose precision like we can for numeric fields.