Thanks, it turns out that some CRT library time-related functions fail to work if a string contains a unicode character. I have changed my time evaluation routine to get around this in the next version.