I don't think cr_items.name is the same as acs_objects.name would be. cr_items.name is a terrible misnomer - it should be sth like cr_items.urlpart since that's what it is. cr_items.name (should) contain a short, lowercase identifier with url compatible characters only, and unique within a particular content folder. All requirements that acs_objects.name wouldn't have. The pretty name of a cr_item can be found in cr_revisions.title instead.
acs_objects.name would ideally duplicate the cr_revisions.title of the live revision, or last revision if there is no live revision.
Adding acs_objects.name would centralize a facility that many packages have already - to store a pretty user displayable name for specific objects. E.g. forums_messages.subject or surveys.name. It would propably be advisable for the packages to move storage of name over to the centralised service. Or think about doing all this in the CR (sorry just rambling).
If it goes into acs_objects, then a null value in acs_objects.name could become 'One acs_object_types.pretty_name', e.g. 'One User Portrait' when displayed.
