One additional side-effect of this (which I forgot to mention before) is that by doing this you lose the context-sensitive aspects of the OOTB menu items - like having it determine that the menu item should be inactive when you're not in a workarea or when you have a directory instead of a file selected, or nothing selected, etc.
Adam,Is this still a problem with TS 6.5 ? Customized items doesnt get disabled automatically when user doesnt have access to the correct area? For example if user doesnt have access to workarea work in the branch A then Delete is disabled but when we put customized item in place it shows enabled.This is kind a security threat in the system. Do we need to handle this in our customized code or some easy ways to achieve this?