Build 200703271800

Rename Type should return a warning when the refactoring will change the 
current behavior. 
Steps to reproduce: Rename Type A to B in the following:
class A{
	   static int length = 17;
	   int m(int[] B){
	     return A.length;
	   }
}

yields the following refactored class:
class B{
	   static int length = 17;
	   int m(int[] B){
	     return B.length;
	   }
}

Note: The same problem occurs when B is a field, a local variable or a 
parameter of Class A or a Class that makes reference to A.length. In addition, 
B can be declared in an interface or class like in the following 2 cases:
- Rename A to B, where field B is declared in interface I
public class A{
	public static int length(){ return 0;};
}
interface I{
	String B= "fred";
}
class FF implements I{
	int m(){
		return A.length();
	}
}

- Rename A to B where field B is declared in class F
public class A{
	public static int length(){ return 0;};
}
class F{
	String B;
}
class FF extends F{
	int m(){
		return A.length();
	}
}