I'm wondering if something changed in the last couple versions with regards to the Membership system and the built-in Login/Register macros?

In looking at the Register partial view it appears as though it should be looping through any custom membership properties I created an displaying them on the form:

@if (registerModel.MemberProperties != null)
{
    for (var i = 0; i < registerModel.MemberProperties.Count; i++)
    {
        @Html.LabelFor(m => registerModel.MemberProperties[i].Value, registerModel.MemberProperties[i].Name)
        @* 
            By default this will render a textbox but if you want to change the editor template for this property you can easily change it. For example, if you wanted to render a custom editor for this field called "MyEditor" you would create a file at ~/Views/Shared/EditorTemplates/MyEditor.cshtml", then you will change the next line of code to render your specific editor template like:
            @Html.EditorFor(m => profileModel.MemberProperties[i].Value, "MyEditor")
        *@
        @Html.EditorFor(m => registerModel.MemberProperties[i].Value)
        @Html.HiddenFor(m => registerModel.MemberProperties[i].Alias)
        <br />
    }
}

However, it still only shows Name, Email, and Password.

I was most likely going to customize this anyway because I want a specific order to the fields. However, I'm concerned that the custom MemberProperties are not being taken into account on the stock Register form.