For a project I am currently working on, I am interested in allowing users to provide multiple e-mail addresses, both for contact purposes as well as providing address book-based social matching. I plan to write a custom membership provider (aspnet_Membership table is too heavy for my liking), but the MembershipProvider system only allows for one e-mail address per account.
What would be the best idea for using the membership provider system but allow for multiple e-mail addresses per user? Or should I avoid MembershipProvider completely and roll my own system?