Hi. An update: I was able to confirm that this is indeed a sw bug added in the recent version 2.18.18. Another suunto 3 watch with the previous sw version did not have this issue. After being upgraded to the last version the problem appeared.
Suunto team, here is another issue to fix in the next version. 🙂
Alon