We are comprehensively reviewing our node implementations. You are correct, that the omission here may result in inappropriate precision for the given operations. However, we do not want to introduce potential disruptions for existing user outcomes without addressing this issue more comprehensively. I'm closing this as won't fix, but you can expect to see this issue addressed in later versions.