1. One or more computer readable storage media having a tangible component and having stored thereon a plurality of instructions that, when executed by one or more processors of a device, causes the one or more processors to perform acts comprising: receiving a call from a call site at a computer, the call site having a context; invoking, in response to the call, a dispatch stub, the dispatch stub checking whether the context of the call matches a single context which the dispatch stub is configured; accessing, in an event the context of the call matches the single context, a first pointer which the dispatch stub is configured, the first pointer being a pointer to a first target code to be executed to carry out the call; executing the first target code to carry out the call; checking whether a frequency which the single context is not matching the contexts of calls received from the call site exceeds a threshold frequency; in the event: the frequency which the single context is not matching the contexts of calls received from the call site exceeds the threshold frequency, then bypassing the dispatch stub and invoking, in response to the call, a resolve stub; or the context of the call does not match the single context, invoking the resolve stub, the resolve stub: checking whether the context of the call matches one of one or more contexts maintained by the resolve stub, the resolve stub further maintaining an association of each context of the one or more contexts with a different target code; accessing, in the event the context of the call matches one of the one or more contexts stored in the resolve stub, a second pointer to second target code to be executed to carry out the call; and executing the second target code to carry out the call; and invoking, in the event the context of the call does not match one of the one or more contexts stored in the resolve stub, a resolver to determine a third pointer to third target code to be executed to carry out the call, wherein: the resolver determines the third pointer to third target code to be executed to carry out the call by: searching through an inheritance hierarchy that includes a type of an object on which the call is made, each type in the inheritance hierarchy including one or more implementation tables and one or more slot maps, the searching beginning with the type of the object and progressing in an order from child type to parent type until a first slot map is located, the first slot map comprising one or more entries, each entry comprising: a type value used as an identifier of either the type that is associated with the first slot map or an identifier for an interface method that is implemented by the type associated with the first slot map; a slot value that identifies a slot within the object that is associated with the type value; an index value representing a slot number used for an interface method that is implemented by the type or an implementation index used for a method implemented by the type; and a scope value that specifies whether the index value is the implementation index associated with an implementation table or a slot number associated with a conceptual slot; in an event that the index value of a first entry is an implementation index associated with the implementation table: accessing the implementation table to retrieve the pointer to the third target code; retrieving, from the location of the implementation table, a pointer to code; and using the retrieved pointer to code as the third pointer; in the event that the index value of the first entry is a slot number associated with the conceptual slot, mapping the conceptual slot for an interface method to a second entry having the type value to assist in retrieving a pointer to the third target code; and in response to the resolver identifying the third target code, the resolver: executes the third target code to carry out the call; and updates data of the resolve stub so that when a subsequent call from the call site having the context is received, the resolve stub executes the third target code to carry out the call without invoking the resolver, thereby facilitating virtual method dispatching.