This is indeed a bug. It seems that it was addressed in OW 2.0 in February 2019, as reported in this post. I recompiled and linked with Open Watcom 2.0 and it worked as expected.