Membership Provider - Users Question

[Guy]

I have much more data to store (e.g. FirstName, LastName, Streetname, ...)
for a Profile/Account then aspnet_users stores. This Profile/Account data
probably will be stored (due to normalization) in more then 1 table.

Now my question: if possible I would like using the standard Membership
provider delivered by ASP.NET 2.0. What is the most used/best practice for
solving the kind of problem I face:
- using the Membership Provider tables (users, roles, ...) as-is and using
foreign keys from my table(s) to the aspnet_users table?
- developing a custom membership provider?
- using a Profile section?
- ...?

Thanks for any suggestion.