Ref's interface is inconsistent with Rugged's API
!103 (merged) introduced an optimization where a Refs target would point to the dereferenced object, which saved us a lot operations, but became inconsistent with Rugged's API, where target would always reference the immediate object pointed at. Consider adding a new property, dereference_target to be consistent with Rugged but still be able to get the target efficiently.