“Inline method” refactoring causes changes in calling relationships

Before the method is refactored, the m() method of the parent class is called. After the refactoring, the m() method of the child class is called. The calling relationship changes.
Code before refactoring:
```java

class A {
void m(Object m) {
System.out.println("A");
}
// inline method 'test()'
void test() {
m("1");
}
}

class B extends A {
void m(Object m) {
System.out.println("B");
}

void f() {
test();
}
}
```
Code after refactoring:
```java
class A {
void m(Object m) {
System.out.println("A");
}
}

class B extends A {
void m(Object m) {
System.out.println("B");
}

void f() {
m("1");
}
}
```

Reproduce the issue using the Java snippets in the report and the Inline Method refactoring. Trace how method resolution changes when test() is inlined into the subclass, then verify that the refactoring preserves the original calling relationship and that the example continues to dispatch to A.m(Object).

Written by the indexing model from the issue text.