The dues-paying unit of membership in my organization is not the individual, but rather the household, (or, more crudely, the street address). The household is comprised of one or more individuals. One such individual in the household pays the dues, is contacted about renewals, dunned, etc. Each individual in the household (inheriting from the household) receives emails, newsletters, membership cards, voting rights, and appears on rosters and directories, has membership rights to forums and website inquiries, etc. based on the status of the household but is otherwise not contacted about dues payment unless that person is also the designee (or head, if you will) of the household. The dues structure is single tier. I haven't seen how your tables could be forced to accommodate this organizational structure, and there is no appetite to change our organizational structure to be able to take advantage of your systems. Accordingly, I'm well into the process of designing tables that reflect our structure. I can continue on the path I'm on or be receptive to any suggestions you might wish to make about reconciling my needs within your system. I await your comments.
Unfortunately, aMember currently does not have support for this feature, and to be honest, it will be extremelly hard to implement. However, I can be wrong here, may be I don't see a simple way.