Use the Absence of Driver Data as an Allocation Filter
In cases where members in your destination range that should receive an allocation are scattered among members that should not receive an allocation, keep in mind that just because a member is part of the destination it does not automatically receive an allocated amount. The allocations are only sent to destinations that have a driver value.
Using this behavior of the allocation engine to your advantage, you can create a single rule that crosses a wider range of sources and destinations but will only allocate to the intersections where it finds driver data. This allows you to create a single rule, where in a legacy system, you may have had to create many rules.