anchor.diff:  %% @spec increment_vclock(riak_object(), vclock:vclock_node()) -> riak_object()
   increment_vclock(Object=#r_object{bucket=B}, ClientId) ->
       NewClock = vclock:increment(ClientId, Object#r_object.vclock),
  -    {ok, Dot} = vclock:get_entry(ClientId, NewClock),
  +    {ok, Dot} = vclock:get_dot(ClientId, NewClock),
       assign_dot(Object#r_object{vclock=NewClock}, Dot, dvv_enabled(B)).
   
   %% @doc  Increment the entry for ClientId in O's vclock.
   -spec increment_vclock(riak_object(), vclock:vclock_node(), vclock:timestamp()) -> riak_object().
   increment_vclock(Object=#r_object{bucket=B}, ClientId, Timestamp) ->
       NewClock = vclock:increment(ClientId, Timestamp, Object#r_object.vclock),
  -    {ok, Dot} = vclock:get_entry(ClientId, NewClock),
  +    {ok, Dot} = vclock:get_dot(ClientId, NewClock),
       %% If it is true that we only ever increment the vclock to create
       %% a frontier object, then there must only ever be a single value
       %% when we increment, so add the dot here.
  
positive.code:                     %% should be identical, but Skewed Dots mean we
                      %% can't guarantee that, the merge will dedupe for
                      %% us.
                      DC = get_drop_candidate(Dot, Drop),
                      MergeAcc#merge_acc{keep=[C0, DC | Keep]};
                  {true, false} ->
                      %% The `dot' is dominated by the other object's
  
negative.code:             %% merge the new object and the old object.
              MergedClock = vclock:merge([PutVC, LocalVC]),
              FrontierClock = vclock:increment(Actor, Timestamp, MergedClock),
              {ok, Dot} = vclock:get_dot(Actor, FrontierClock),
              %% Assign an event to the new value
              Bucket = bucket(OldObject),
              DottedPutObject = assign_dot(NewObject, Dot, dvv_enabled(Bucket)),
  