Most people seem to agree that long methods are a code smell - a sign something may not be quite right with the code contained in them.

Which tools do you use to detect this smell?

clarified title based on responses. also, remember:

• Your code will live over time, and be edited by multiple programmers
• Emergency fixes and changes will come in, late at night, when the writer is too tired to pay attention to smells
• Different programmers use different tools. A contractor with 4 screens set at maximum resolution will have a different idea of acceptable method size

In this context, I'm looking for tools and methods which go beyond looking at the size of a method when it's written, or when it's being edited.