Using a method name as a value is now flagged at design time

Passing a bare method name where a callback is expected, for example tb.SortWith(myMethodSort) instead of tb.SortWith(AddressOf myMethodSort), previously compiled without any warning and only failed when the app ran. Objo now reports this at design time and suggests calling the method (myMethodSort()) or wrapping it with AddressOf.