SmartMerge and RootOrder conflict

Hi,
I've made a simple test of adding, renaming and removing GameObject in a scene, and the only element that SmartMerge seemed to fail on are the value of m_RootOrder when the value has been changed on both side because of add/delete of other elements which are properly auto-resolved.

Since the add/remove of gameobject was properly resolved, shouldn't this field's value be deducible from where the merge node is in the yaml file hierarchy or from the order of their file id in their parent's transform' m_Children yaml segment? Or isn't it sanitize in any way at runtime when loading the scene?

It's one of those conflict that's potentially scary for LevelDesigner to solve since they have no exposure to the meaning of the field.

Cheers!