short's shortcomings

Sorry, but I could not resist that subject.  However the shortcoming to 
which I refer is this. Consider the following

class    CLOCK
inherit  COUNTER
rename  value  as  time  end
export   {NONE}  all;
             {ANY}  time;
             {CLOCK_CONTROLLER}  increment
end

The short view, maintaining the original description, shows
time : INTEGER;    -- The value of the counter.
Now the value of the counter has no relevance to a client using a 
simulated time.
A mechanism for associating a replacement descriptive comment when 
features are renamed would add to the usefulness of "short" documentation.
Could you consider such a capability.
Regards
Frank Salter