In my opinion, that is a terrible limitation as it works against the concept of using ABCGs. The only solution is to spam traps to all of the individual collectors in a group, hoping you hit the one that's polling your device. If you ever have to extend your ABCG, now you have to touch all of your infrastructure to add a new trap destination as well..
It shouldn't be difficult to have all Collectors ingest traps and assign them to the proper resource/collector via some back-end mechanism... When I've brought this up to folks at LM, they recommend not using traps in the first place, polling for everything. That's a nice idea, but not exactly feasible to accomplish day 1 when you're moving your whole organization into this product (if it's even truly possible to get away from traps completely).
