This is caused by data type conversion: DATE is a double float and the unix time is an integer. The correct fix would be rounding to the next full second:

utm(wdate(0)+0.5/(1440.*60.))

I've put a notice to the developers for doing that on the next occasion. It is not related to 2.15.