Provide User/Custom Fields in Object Definitions

I would like to have a few user/custom fields available in the object definitions for the ability to add custom information about the object. One of the very important pieces of information we need to track for objects is the OWNER for monitoring purposes. Having the owner documented in the object definition allows us to alert the owner of the object directly when there is a problem instead of alerting the system administrators or help desk for everything and then they looking up the owner of the object to notify. Without a user/custom field for this data, we have had to steal half of the description for this which does not leave much room for the description itself. Another piece of information we store is when the object was last reviewed for its usage. We keep track of when queues were last put to and gotten from, and then when a queue has not had either of these events for a year we review for usage and check with the owner if they still need the queue or not. For this data, we stole another unused text field in the object definition. I could see the possibility of storing more customized information in the object definition if we had some fields to keep it. This would be very helpful functionality. Each field would not have to be that large - maybe 48 or 64 bytes each. A minimum of 3 fields would be desirable.