Currently, Name mapping behaves/works as a reference especially when testing web pages or .net programs. When a script is recorded and i am referring to script and not to Keyword test the objects are placed in Name Mapping. On the next step, that a user wants to record a new procedure or wants to add on an existing one TC makes a new reference to already existing object in name mapping.
My suggestion is to pre-load / have the objects saved or stored in the name mapping so that during the recording if an object already exists TC will use it as is instead of making new reference refraining from piling up with the same object. This will make life a lot easier as it creates grounds for multiple recording Techniques. For example a tester can use TC to learn the objects once using the Object Spy and then use them during the creation of the script. A more advance scenario will be to use the object spy on the highest level of objects and the spy to detect all the child objects from the screen and then to place them in Name Mapping with one go. I have seen that in other testing product and provides a great flexibility to the test developer. This will require though to change the Name Mapping approach from reference to storage.
Dear community members, If you wish for me to further expedite on this i will be more than happy to participate or if you should require further information please do not hesitate to contact me.