> The problem is that can.Map morphs the originating object into a much bigger and more complex object with SHEDLOADS of stuff that is only of concern to internal can.Routines and nothing whatever to do with the actual app.
can.Map does not mutate the originating object. It copies it.