Fixed narrow method causes problems with incomplete data (passwords, task result, etc)

The new implementation is correct; however, many times the client calls it on incomplete data that are not marked as such. This is to be resolved somehow.

Current workaround is introduction of assumeIncompleteItems parameter that provides more-or-less previous behavior (in fact, a bit weaker, because even the previous implementation was not correct when facing incomplete objects).