The test script writes min, max and values in the middle of the datatype range.
If a server provides the ValuePrecision property and rounds the values accordingly, the validation fails twice:
1) The CTT validates the written and read value directly in the library for equality
2) The CTT validates the written and read value in the test script for equality

In order to resolve the issue,
1) the built in validation in the library must be deactivated
2) the ValuePrecision property must be read and honored for Float, Double and DateTime.