I always try to keep the workarounds as simple as possible, so they´re easy to manage in the long run. For revisions, I would say it depends what you are the revisions for. As Brian said, some offices will do it per sheet, or per set.
Since I usually deal with project wide changes/revisions (moving walls, changing window sizes, etc) that affect other disciplines, I revision per project change; so what I do is I keep about ten revision layers (Revision01, Revision02) and use the Olivier Dentan great revision cloud object and apply it directly on the floor plan, with the label using the format "01.03", which would be "revision#.change id" and a verbose description of each change in a separate layout named, obviously, "revisions".
I place as many clouds as needed in its own layer, so I can turn on each cloud set based by revision#. When moving to revision 2, I just turn off Revision01 layer and since those changes are kept in the verbose log, we don't need to show them anymore, just the current changes are highlighted with the new clouds (i.e. revision02).
Now, remember that layer settings are different for model and layouts, so you can have a different set of layers if you need to revision per sheet and they won't get in the way of the model combos.
So if I had to deal with MEP or HVAC revisions, I would keep them per sheet, since it would be easier to manage as clouds for Mechanical might not be needed on the Electrical layouts, and if put directly in model, you would need a whole other set of layers to manage those.
Hope I explained myself.
Cheers.
