armobjcopy mistakenly puts many zero bytes at the start of a binary file

In some instances, when armobjcopy is used to create a binary file with a command similar to ...

armobjcopy -O binary file.out file.bin

... binary file created incorrectly starts with many zero bytes. Suppose, for example, the first initialized section has the address 0x2000. The binary file should begin with first byte from that first section. But it doesn't. Instead, it starts with 0x2000 bytes of zero.