What about extending syntax of WhenCalled with this?

Recent TypeMock version simplifies a lot faking certain elements of collections:

Isolate.WhenCalled(() => MyCollection["abc"]).WillReturn("123");
Isolate.WhenCalled(() => MyCollection["def"]).WillReturn("456");

TypeMock memorizes values of collection elements associated with specific index values, so it is now possible to set different expectations on different collection elements.

Unfortunately for method calls it does not work the same way:

// Does not work this way!
Isolate.WhenCalled(() => MyProducts.GetPrice("abc")).WillReturn("123");
Isolate.WhenCalled(() => MyProducts.GetPrice("def")).WillReturn("456");

What would be great if developer could bind expectations with parameters, moreover if he could control what parameter values should be bound.

Like this:
Isolate.WhenCalled((x) => MyProducts.GetPrice(x)).WillReturn("123");
Isolate.WhenCalled(() => MyProducts.GetPrice("abc")).WillReturn("456");

The first statement leaves the argument of GetPrice unbound, i.e. no matter what is sent, GetPrice will return "123". The second statement binds result "456" to explicitly set argument "abc".

Another example, let's say we have a method Add:
int Add(int,int).

Here what we can do to it:

// Sets expectation for specific first and second arguments
Isolate.WhenCalled(() => Calc.Add(1,2)).WillReturn(3);
// Sets expectation for specific second argument
Isolate.WhenCalled<int>((x) => Calc.Add(x,2)).WillReturn(3);
// Sets expectation for any argument
Isolate.WhenCalled<int>((x,y) => Calc.Add(x,y)).WillReturn(3);

Of course right now these examples won't even compile. They will require adding new overloads to Isolate.WhenCalled.

In addition to Isolate.WhenCalled(Action):
Isolate.WhenCalled<T>(Action<T>)
Isolate.WhenCalled<T1>(Action<T1>)
etc...

What do you think about such way of controlling parameterized fakes?