Porting token.module in Drupal core code

Using token.module to handle the tokens actually makes sense when it is possible to use the node tokens, and the node uses some CCK fields. Differently, to use token.module to replace the few tokens populated from the user data doesn't make any sense. If then, as in most settings pages handled by Drupal core code, the need is to handle few tokens for global values, to use token.module simply makes the code slower, and more inefficient.