Try contacting EPiServer support to determine if this is a bug or by design: http://world.episerver.com/Support/
There is also a forum dedicated to feature requests which is monitored by EPiServer employees, try posting there: http://world.episerver.com/Modules/Forum/Pages/Forum.aspx?id=18602&epslanguage=en
I have a suggestion for EPiServer CMS. I was not sure about where I should post it, so I am posting it here. In EPiServer we have a UpdatedUser Event which as name suggests should fire after the user is updated. But this is not the case I saw the code using reflector and found that the updateuser method first performs all the database operations and then fires OnUpdateUser event, but point is that all database operations are fired within a transaction. Hence if we try to perform additional tasks on the user object like if we try to again fetch any user detail from the database within that event to perform our business scenarios, we do not get the latest updated user data but the data that was not yet updated.